-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Polish metrics page and flow #2461
base: main
Are you sure you want to change the base?
Conversation
… in output page, fix styles
…essary imports, remove alert component
I can't find the new UI. Was the tab lost in the merge? |
The tab is not lost but the file is called "logging" so I didn't want to do the full renaming of the tab before talking with a native speaker (as we discuss in K&K), so now in the branch we see the "report" file that is the old one. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this looks really nice now, and the code looks mostly very good as well. But the text needs to be internationalized and there are some minor code style issues that I've commented on below.
src/pages/organize/[orgId]/projects/[campId]/areaassignments/[areaAssId]/report.tsx
Outdated
Show resolved
Hide resolved
src/pages/organize/[orgId]/projects/[campId]/areaassignments/[areaAssId]/report.tsx
Outdated
Show resolved
Hide resolved
src/pages/organize/[orgId]/projects/[campId]/areaassignments/[areaAssId]/report.tsx
Outdated
Show resolved
Hide resolved
src/pages/organize/[orgId]/projects/[campId]/areaassignments/[areaAssId]/report.tsx
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some questions that arose from playing around with the deployed version!
src/pages/organize/[orgId]/projects/[campId]/areaassignments/[areaAssId]/report.tsx
Outdated
Show resolved
Hide resolved
justifyContent="space-between" | ||
width="100%" | ||
|
||
{metricBeingDeleted?.definesDone && ( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree. I'm leaning towards removing the option to delete the only yes/no question if there are no other questions to choose from. Alternatively, we could display a message like: 'To delete {question}, you must first create a new choice question that defines if the mission was successful.' What do you think @ziggabyte ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think i have good judgement around this type of UX flow 😂 I don't know honestly, I think it should be asked to the designers and/or richard because I think they have an idea of how this should flow that i don't remember...
Description
This PR implements a new design for "outcomes" page, now renamed as "report" page. It polishes the creation, listing, deletion and edition of metrics for the canvas assignment.
Screenshots
Changes
Outcomes
tab forReport
Choise Metrics
fromScale Metrics
Edit
andDelete
buttons for iconsCheckbox
in edit modeModal
to open in edit modeModal
before deleting a metricNotes to reviewer
None
Related issues
None